Identifying unauthorized communication systems based on their memory contents

ABSTRACT

An authorized client communication system seeking access to a host communication system may be identified by locating a memory segment within the client communication system that stores client software used to access the host computer system. The memory segment then is examined to determine whether the client software stored in the memory segment corresponds to client software for an official client communication system. Communications from the client communication system are terminated when the client software in the memory segment is determined to diverge from software for an official client communication system.

CROSS REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. application Ser. No.09/749,638, filed Dec. 28, 2000, now abandoned, and claims the benefitof U.S. Provisional Application Ser. No. 60/218,243, filed Jul. 14,2000, which is incorporated by reference.

TECHNICAL FIELD

This invention relates to identifying unauthorized communicationsystems.

BACKGROUND

For two or more computer systems to communicate, at least one of thosesystems is generally configured with software enabling thecommunication. For instance, in a computer network configured forclient-server communications, the client system is configured withclient software that enables access to and interaction with the serversystem.

Systems employing client-server communications may be subject tosecurity attacks. One form of security attack involves the use of anunauthorized client system that imitates an authorized client system toachieve the access ordinarily reserved for authorized client systems.

SUMMARY

A host communication system (e.g., an online service provider) maydefend against certain security attacks by determining whether a clientcommunication system (e.g., a personal computer) is an authorizedcommunication system. The determination may be performed during aninitiation of the communication session, or at some later time.

In one general aspect, an authorized client communication system seekingaccess to a host communication system may be identified by locating amemory segment within the client communication system that stores clientsoftware used to access the host computer system. The memory segmentthen is examined to determine whether the client software stored in thememory segment corresponds to client software for an official clientcommunication system. Communications from the client communicationsystem are terminated when the client software in the memory segment isdetermined to diverge from client software for an official clientcommunication system.

Implementations may include one or more of the following features. Forexample, locating the memory segment may include identifying a type orversion of the client software being used by the client communicationsystem to enable communication, and locating the memory segment of theclient communication system based on the identified type or version. Thetype or version of the client software may be identified by, forexample, receiving information from the client communication systemindicating the type or version of the client software. This informationmay be received when the communication session is initiated, or at someother time. The type or version also may be determined by performing adiagnostic on the client communication system to automatically determinethe type or version.

Locating the memory segment may include locating a memory segment of theclient communication system that includes client software remainingunchanged in a corresponding memory segment of an official clientcommunication system, where the memory segment that is located may beuser independent. Locating the memory segment also may includeidentifying a memory segment based on a random selection among severalmemory segments that store client software, that are user independent,and/or that remain unchanged between different systems.

To determine whether the client software stored in the located memorysegment corresponds to predictable client software for an officialclient communication system, the client software stored in the memorysegment may be compared with the corresponding client software of theofficial client communication system. This comparison may be made byperforming a mathematical computation on the contents of the memorysegment and comparing the result of the mathematical computation againstthe results of a corresponding mathematical computation on thecorresponding client software of the official communication system. Themathematical computations may include, for example, a check sum, ahashing algorithm, a MessageDigest™ (MD5) algorithm, or a Securehashalgorithm (SHA1).

Implementations may include a method or process, an apparatus or system,or computer software on a computer medium.

The details of one or more implementation are set forth in theaccompanying drawings and the description below. Other features andadvantages will be apparent from the description and drawings, and fromthe claims.

DESCRIPTION OF DRAWINGS

FIG. 1 is a block diagram illustrating an exemplary communication systemcapable of identifying unauthorized communication systems.

FIGS. 2-6 are diagrams illustrating various aspects of the communicationsystem of FIG. 1.

FIG. 7 is a block diagram illustrating a logical configuration ofsoftware elements within the communication system of FIG. 1.

FIG. 8 is a flowchart of a process performed in response to anauthentication failure.

FIG. 9 is a block diagram illustrating logical elements of the system ofFIG. 1.

FIGS. 10A-10C are process flowcharts showing aspects of the process ofFIG. 9.

Like reference symbols in the various drawings indicate like elements.

DETAILED DESCRIPTION

For illustrative purposes, FIGS. 1-6 describe a communications systemfor implementing techniques for transferring files between subscribersof an instant messaging host complex. For brevity, several elements inthe figures described below are represented as monolithic entities.However, as would be understood by one skilled in the art, theseelements each may include numerous interconnected computers andcomponents designed to perform a set of specified operations and/ordedicated to a particular geographical region.

Referring to FIG. 1, a communications system 100 is capable ofdelivering and exchanging data between a client system 105 and a hostsystem 110 through a communications link 115. The client system 105typically includes one or more client devices 120 and/or clientcontrollers 125. For example, the client system 105 may include one ormore general-purpose computers (e.g., personal computers), one or morespecial-purpose computers (e.g., devices specifically programmed tocommunicate with each other and/or the host system 110), or acombination of one or more general-purpose computers and one or morespecial-purpose computers. The client system 105 may be arranged tooperate within or in concert with one or more other systems, such as forexample, one or more LANs (“Local Area Networks”) and/or one or moreWANs (“Wide Area Networks”).

The client device 120 is generally capable of executing instructionsunder the command of a client controller 125. The client device 120 isconnected to the client controller 125 by a wired or wireless datapathway 130 capable of delivering data.

The client device 120 and client controller 125 each typically includesone or more hardware components and/or software components. An exampleof a client device 120 is a general-purpose computer (e.g., a personalcomputer) capable of responding to and executing instructions in adefined manner. Other examples include a special-purpose computer, aworkstation, a server, a device, a component, other physical or virtualequipment or some combination thereof capable of responding to andexecuting instructions. An example of client controller 125 is asoftware application loaded on the client device 120 for commanding anddirecting communications enabled by the client device 120. Otherexamples include a program, a piece of code, an instruction, a device, acomputer, a computer system, or a combination thereof, for independentlyor collectively instructing the client device 120 to interact andoperate as described herein. The client controller 125 may be embodiedpermanently or temporarily in any type of machine, component, physicalor virtual equipment, storage medium, or propagated signal capable ofproviding instructions to the client device 120.

The communications link 115 typically includes a delivery network 160making a direct or indirect communication between the client system 105and the host system 110, irrespective of physical separation. Examplesof a delivery network 160 include the Internet, the World Wide Web,WANs, LANs, analog or digital wired and wireless telephone networks(e.g. PSTN, ISDN, and xDSL), radio, television, cable, satellite, and/or any other delivery mechanism for carrying data. The communicationslink 115 may include communication pathways 150, 155 that enablecommunications through the one or more delivery networks 160 describedabove. Each of the communication pathways 150, 155 may include, forexample, a wired, wireless, cable or satellite communication pathway.

The host system 110 includes a host device 135 capable of executinginstructions under the command and direction of a host controller 140.The host device 135 is connected to the host controller 140 by a wiredor wireless data pathway 145 capable of carrying and delivering data.

The host system 110 typically includes one or more host devices 135and/or host controllers 140. For example, the host system 110 mayinclude one or more general-purpose computers (e.g., personalcomputers), one or more special-purpose computers (e.g., devicesspecifically programmed to communicate with each other and/or the clientsystem 105), or a combination of one or more general-purpose computersand one or more special-purpose computers. The host system 110 may bearranged to operate within or in concert with one or more other systems,such as, for example, one or more LANs (“Local Area Networks”) and/orone or more WANs (“Wide Area Networks”).

The host device 135 and host controller 140 each typically includes oneor more hardware components and/or software components. An example of ahost device 135 is a general-purpose computer (e.g., a personalcomputer) capable of responding to and executing instructions in adefined manner. Other examples include a special-purpose computer, aworkstation, a server, a device, a component, other physical or virtualequipment or some combination thereof capable of responding to andexecuting instructions. An example of host controller 140 is a softwareapplication loaded on the host device 135 for commanding and directingcommunications enabled by the host device 135. Other examples include aprogram, a piece of code, an instruction, a device, a computer, acomputer system, or a combination thereof, for independently orcollectively instructing the host device 135 to interact and operate asdescribed herein. The host controller 140 may be embodied permanently ortemporarily in any type of machine, component, physical or virtualequipment, storage medium, or propagated signal capable of providinginstructions to the host device 135.

FIG. 2 illustrates a communication system 200 including a client system205 communicating with a host system 210 through a communications link215. Client system 205 typically includes one or more client devices 220and one or more client controllers 225 for controlling the clientdevices 220. Host system 210 typically includes one or more host devices235 and one or more host controllers 240 for controlling the hostdevices 235. The communications link 215 may include communicationpathways 250, 255 enabling communications through the one or moredelivery networks 260.

Examples of each element within the communication system of FIG. 2 arebroadly described above with respect to FIG. 1. In particular, the hostsystem 210 and communications link 215 typically have attributescomparable to those described with respect to host system 110 andcommunications link 115 of FIG. 1, respectively. Likewise, the clientsystem 205 of FIG. 2 typically has attributes comparable to and mayillustrate one possible embodiment of the client system 105 of FIG. 1.

The client device 220 typically includes a general purpose computer 270having an internal or external storage 272 for storing data and programssuch as an operating system 274 (e.g., DOS, Windows™, Windows 95™,Windows 98™, Windows 2000™, Windows NT™, OS/2, and Linux) and one ormore application programs. Examples of application programs includeauthoring applications 276 (e.g., word processing, database programs,spreadsheet programs, and graphics programs) capable of generatingdocuments or other electronic content; client applications 278 (e.g.,AOL client, CompuServe client, AIM client, AOL TV client, and ISPclient) capable of communicating with other computer users, accessingvarious computer resources, and viewing, creating, or otherwisemanipulating electronic content; and browser applications 280 (e.g.,Netscape's Navigator and Microsoft's Internet Explorer) capable ofrendering standard Internet content.

The general-purpose computer 270 also includes a central processing unit282 (CPU) for executing instructions in response to commands from theclient controller 225. In one implementation, the client controller 225includes one or more of the application programs installed on theinternal or external storage 272 of the general-purpose computer 270. Inanother implementation, the client controller 225 includes applicationprograms externally stored in and performed by one or more device(s)external to the general- purpose computer 270.

The general-purpose computer typically will include a communicationdevice 284 for sending and receiving data. One example of thecommunication device 284 is a modem. Other examples include atransceiver, a set-top box, a communication card, a satellite dish, anantenna, or another network adapter capable of transmitting andreceiving data over the communications link 215 through a wired orwireless data pathway 250. The general-purpose computer 270 also mayinclude a TV (“television”) tuner 286 for receiving televisionprogramming in the form of broadcast, satellite, and/or cable TVsignals. As a result, the client device 220 can selectively and/orsimultaneously display network content received by communications device284 and television programming content received by the TV tuner 286.

The general-purpose computer 270 typically will include an input/outputinterface 288 to enable a wired or wireless connection to variousperipheral devices 290. Examples of peripheral devices 290 include, butare not limited to, a mouse 291, a mobile phone 292, a personal digitalassistant 293 (PDA), a keyboard 294, a display monitor 295 with orwithout a touch screen input, and/or a TV remote control 296 forreceiving information from and rendering information to subscribers.Other examples may include voice recognition and synthesis devices.

Although FIG. 2 illustrates devices such as a mobile telephone 292, aPDA 293, and a TV remote control 296 as being peripheral with respect tothe general-purpose computer 270, in another implementation, suchdevices may themselves include the functionality of the general-purposecomputer 270 and operate as the client device 220. For example, themobile phone 292 or the PDA 293 may include computing and networkingcapabilities and function as a client device 220 by accessing thedelivery network 260 and communicating with the host system 210.Furthermore, the client system 205 may include one, some or all of thecomponents and devices described above.

Referring to FIG. 3, a communications system 300 is capable ofdelivering and exchanging information between a client system 305 and ahost system 310 through a communication link 315. Client system 305typically includes one or more client devices 320 and one or more clientcontrollers 325 for controlling the client devices 320. Host system 310typically includes one or more host devices 335 and one or more hostcontrollers 340 for controlling the host devices 335. The communicationslink 315 may include communication pathways 350, 355 enablingcommunications through the one or more delivery networks 360.

Examples of each element within the communication system of FIG. 3 arebroadly described above with respect to FIGS. 1 and 2. In particular,the client system 305 and the communications link 315 typically haveattributes comparable to those described with respect to client systems105 and 205 and communications links 115 and 215 of FIGS. 1 and 2,respectively. Likewise, the host system 310 of FIG. 3 may haveattributes comparable to and may illustrate one possible embodiment ofthe host systems 110 and 210 shown in FIGS. 1 and 2, respectively.

The host system 310 includes a host device 335 and a host controller340. The host controller 340 is generally capable of transmittinginstructions to any or all of the elements of the host device 335. Forexample, in one implementation, the host controller 340 includes one ormore software applications loaded on the host device 335. However, inother implementations, as described above, the host controller 340 mayinclude any of several other programs, machines, and devices operatingindependently or collectively to control the host device 335.

The host device 335 includes a login server 370 for enabling access bysubscribers and routing communications between the client system 305 andother elements of the host device 335. The host device 335 also includesvarious host complexes such as the depicted OSP (“Online ServiceProvider”) host complex 380 and IM (“Instant Messaging”) host complex390. To enable access to these host complexes by subscribers, the clientsystem 305 may include communication software, for example, an OSPclient application and an IM client application. The OSP and IMcommunication software applications are designed to facilitate thesubscriber's interactions with the respective services and, inparticular, may provide access to all the services available within therespective host complexes. For example, Instant Messaging allows asubscriber to use the IM client application to view whether particularsubscribers (“buddies”) are online, exchange instant messages withparticular subscribers, participate in group chat rooms, trade filessuch as pictures, invitations or documents, find other subscribers withsimilar interests, get customized news and stock quotes, and search theWeb.

Typically, the OSP host complex 380 supports different services, such asemail, discussion groups, chat, news services, and Internet access. TheOSP host complex 380 is generally designed with an architecture thatenables the machines within the OSP host complex 380 to communicate witheach other, certain protocols (i.e., standards, formats, conventions,rules, and structures) being employed to enable the transfer of data.The OSP host complex 380 ordinarily employs one or more OSP protocolsand custom dialing engines to enable access by selected clientapplications. The OSP host complex 380 may define one or more specificprotocols for each service based on a common, underlying proprietaryprotocol.

The IM host complex 390 is generally independent of the OSP host complex380, and supports instant messaging services irrespective of asubscriber's network or Internet access. Thus, the IM host complex 390allows subscribers to send and receive instant messages, whether or notthey have access to any particular ISP. The IM host complex 390 maysupport associated services, such as administrative matters,advertising, directory services, chat, and interest groups related tothe instant messaging. The IM host complex 390 has an architecture thatenables all of the machines within the IM host complex to communicatewith each other. To transfer data, the IM host complex 390 employs oneor more standard or exclusive IM protocols.

The host device 335 may include one or more gateways that connect andtherefore link complexes, such as the OSP host complex gateway 385 andthe IM host complex gateway 395. The OSP host complex gateway 385 andthe IM host complex 395 gateway may directly or indirectly link the OSPhost complex 380 with the IM host complex 390 through a wired orwireless pathway. Ordinarily, when used to facilitate a link betweencomplexes, the OSP host complex gateway 385 and the IM host complexgateway 395 are privy to information regarding a protocol anticipated bya destination complex, which enables any necessary protocol conversionto be performed incident to the transfer of data from one complex toanother. For instance, the OSP host complex 380 and IM host complex 390may use different protocols such that transferring data between thecomplexes requires protocol conversion by or at the request of the OSPhost complex gateway 385 and/or the IM host complex gateway 395.

Referring to FIG. 4, a communications system 400 is capable ofdelivering and exchanging information between a client system 405 and ahost system 410 through a communication link 415. Client system 405typically includes one or more client devices 420 and one or more clientcontrollers 425 for controlling the client devices 420. Host system 410typically includes one or more host devices 435 and one or more hostcontrollers 440 for controlling the host devices 435. The communicationslink 415 may include communication pathways 450, 455 enablingcommunications through the one or more delivery networks 460. As shown,the client system 405 may access the Internet 465 through the hostsystem 410.

Examples of each element within the communication system of FIG. 4 arebroadly described above with respect to FIGS. 1-3. In particular, theclient system 405 and the communications link 415 typically haveattributes comparable to those described with respect to client systems105, 205, and 305 and communications links 115, 215, and 315 of FIGS.1-3, respectively. Likewise, the host system 410 of FIG. 4 may haveattributes comparable to and may illustrate one possible embodiment ofthe host systems 110, 210, and 310 shown in FIGS. 1-3, respectively.However, FIG. 4 describes an aspect of the host system 410, focusingprimarily on one particular implementation of OSP host complex 480.

The client system 405 includes a client device 420 and a clientcontroller 425. The client controller 425 is generally capable ofestablishing a connection to the host system 410, including the OSP hostcomplex 480, the IM host complex 490 and/or the Internet 465. In oneimplementation, the client controller 425 includes an OSP applicationfor communicating with servers in the OSP host complex 480 using OSPprotocols that may or may not be exclusive or proprietary. The clientcontroller 425 also may include applications, such as an IM clientapplication and/or an Internet browser application, for communicatingwith the IM host complex 490 and the Internet 465.

The host system 410 includes a host device 435 and a host controller440. The host controller 440 is generally capable of transmittinginstructions to any or all of the elements of the host device 435. Forexample, in one implementation, the host controller 440 includes one ormore software applications loaded on one or more elements of the hostdevice 435. However, in other implementations, as described above, thehost controller 440 may include any of several other programs, machines,and devices operating independently or collectively to control the hostdevice 435.

The host device 435 includes a login server 470 capable of enablingcommunications between client systems 405 and various elements of thehost system 410, including elements such as OSP host complex 480 and IMhost complex 490. The login server 470 may implement one or moreauthorization procedures to enable simultaneous access to one or more ofthese elements.

The OSP host complex 480 and the IM host complex 490 are typicallyconnected through one or more OSP host complex gateways 485 and one ormore IM host complex gateways 495. Each OSP host complex gateway 485 andEM host complex gateway 495 may generally perform protocol conversionsnecessary to enable communication between one or more of the OSP hostcomplex 480, the IM host complex 490, and the Internet 465.

The OSP host complex 480 supports a set of services to be accessedthrough and/or performed by from one or more servers located internal toand external from the OSP host complex 480. Servers external to the OSPhost complex 480 may communicate using the Internet 465. Serversinternal to the OSP complex 480 may be arranged in one or moreconfigurations. For example, servers may be arranged in largecentralized clusters identified as farms 4802 or in localized clustersidentified as pods 4804.

More specifically, farms 4802 are groups of servers located atcentralized locations within the OSP host complex 480. Farms 4802generally are dedicated to providing particular functionality andservices to subscribers and clients from a centralized location,regardless of the location of the subscriber or client. Farms 4802 areparticularly useful for providing services that depend upon otherremotely-located or performed processes and services for information,such as, for example, chat, email, instant messaging, news, newsgroups,search, stock updates, and weather. Thus, farms 4802 tend to rely onconnections with external resources such as the Internet 465 and/orother servers within the OSP host complex 480.

By contrast to farms 4802, pods 4804 are clusters of localized serversthat provide some services offered by the OSP host complex 480 from alocation local to the service or information recipient, thus reducingand avoiding time delays and congestion inherent in centralizedprocessing. Each pod 4804 includes one or more interrelated serverscapable of operating together to provide one or more services offered bythe OSP host complex 480 in a geographically localized manner, theservers within a pod 4804 generally operating independently rather thanrelying on resources external to the pod 4804 to operate. A pod 4804 maycache content received from external sources, such as farms 4802 or theInternet 465, making frequently requested information readily availableto the local service or information recipients served by the pod 4804.In this way, pods 4804 are particularly useful in providing servicesthat are independent of other processes and servers such as, forexample, routing to other localized resources or recipients, providingaccess to keywords and geographically specific content, providing accessto routinely accessed information, and downloading certain software andgraphical interface updates with reduced processing time and congestion.The determination of which servers and processes are located in the pod4804 is made by the OSP according to load distribution, frequency ofrequests, demographics, and other factors.

In addition to farms 4802 and pods 4804, the implementation of FIG. 4also includes one or more non-podded and non-farmed servers 4806. Ingeneral, the servers 4806 may be dedicated to performing a particularservice or information that relies on other processes and services forinformation and may be directly or indirectly connected to resourcesoutside of the OSP host complex 480, such as the Internet 465 and the IMhost complex 490, through an OSP gateway 4808 within OSP host complexgateway 485. In the event that subscriber usage of a particular serviceor information of the servers 4806 becomes relatively high, thoseservers 4806 may be integrated into a farm or pod as appropriate.

In the implementation of FIG. 4, one particular exemplary pod 4810 isshown in more detail. Pod 4810 includes a routing processor 4812. In apacket-based implementation, the client system 405 may generateinformation requests, convert the requests into data packets, sequencethe data packets, perform error checking and other packet-switchingtechniques, and transmit the data packets to the routing processor 4812.Upon receiving data packets from the client system 405, the routingprocessor 4812 may directly or indirectly route the data packets to aspecified destination within or outside of the OSP host complex 480. Ingeneral, the routing processor 4812 will examine an address field of adata request, use a mapping table to determine the appropriatedestination for the data request, and direct the data request to theappropriate destination.

For example, in the event that a data request from the client system 405can be satisfied locally, the routing processor 4812 may direct the datarequest to a local server 4814 in the pod 4810. In the event that thedata request cannot be satisfied locally, the routing processor 4812 maydirect the data request internally to one or more farms 4802, one ormore other pods 4804, or one or more non-podded servers 4806 in the OSPhost complex 480, or the routing processor 4812 may direct the datarequest externally to elements such as the IM host complex 490 throughan OSP/pod gateway 4816.

The routing processor 4812 also may direct data requests and/orotherwise facilitate communication between the client system 405 and theInternet 465 through the OSP/pod gateway 4816. In one implementation,the client system 405 uses an OSP client application to convert standardInternet content and protocols into OSP protocols and vice versa, wherenecessary. For example, when a browser application transmits a requestin a standard Internet protocol, the OSP client application canintercept the request, convert the request into an OSP protocol and sendthe converted request to the routing processor 4812 in the OSP hostcomplex 480. The routing processor 4812 recognizes the Internet 465 asthe destination and routes the data packets to an IP (“InternetProtocol”) tunnel 4818. The IP tunnel 4818 converts the data from theOSP protocol back into standard Internet protocol and transmits the datato the Internet 465. The IP tunnel 4818 also converts the data receivedfrom the Internet in the standard Internet protocol back into the OSPprotocol and sends the data to the routing processor 4812 for deliveryback to the client system 405. At the client system 405, the OSP clientapplication converts the data in the OSP protocol back into standardInternet content for communication with the browser application.

The IP tunnel 4818 may act as a buffer between the client system 405 andthe Internet 465, and may implement content filtering and time savingtechniques. For example, the IP tunnel 4818 can check parental controlssettings of the client system 405 and request and transmit content fromthe Internet 465 according to the parental control settings. Inaddition, the IP tunnel 4818 may include a number a caches for storingfrequently accessed information. If requested data is determined to bestored in the caches, the IP tunnel 4818 may send the information to theclient system 405 from the caches and avoid the need to access theInternet 465.

In another implementation, the client system 405 may use standardInternet protocols and formatting to access pods 4810 and the Internet465. For example, the subscriber can use an OSP TV client applicationhaving an embedded browser application installed on the client system405 to generate a request in standard Internet protocol, such as HTTP(“HyperText Transport Protocol”). In a packet-based implementation, datapackets may be encapsulated inside a standard Internet tunnelingprotocol, such as, for example, UDP (“User Datagram Protocol”), androuted to a web tunnel 4820. The web tunnel 4820 may be a L2TP (“LayerTwo Tunneling Protocol”) tunnel capable of establishing a point-to-pointprotocol (PPP) session with the client system 405. The web tunnel 4820provides a gateway to the routing processor 4812 within the pod 4810,the Internet 465, and a web proxy 4822.

The web proxy 4822 can look up subscriber information from the IPaddress of the client system 405 to determine demographic informationsuch as the subscriber's parental control settings. In this way, the webproxy 4822 can tailor the subscriber's content and user interfaces. Theweb proxy 4822 can also perform caching functions to store certain URLs(“Uniform Resource Locators”) and other electronic content so that theweb proxy 4822 can locally deliver information to the client system 405and avoid the need to access the Internet 465 in the event that datarequested by the client system 405 has been cached.

Referring to FIG. 5, a communications system 500 is capable ofdelivering and exchanging information between a client system 505 and ahost system 510 through a communication link 515. Client system 505typically includes one or more client devices 520 and one or more clientcontrollers 525 for controlling the client devices 520. Host system 510typically includes one or more host devices 535 and one or more hostcontrollers 540 for controlling the host devices 535. The communicationslink 515 may include communication pathways 550, 555 enablingcommunications through the one or more delivery networks 560. As shown,the client system 505 may access the Internet 565 through the hostsystem 510.

Examples of each element within the communication system of FIG. 5 arebroadly described above with respect to FIGS. 1-4. In particular, theclient system 505 and the communications link 515 typically haveattributes comparable to those described with respect to client systems105, 205, 305, and 405 and communications links 115, 215, 315, and 415of FIGS. 1-4, respectively. Likewise, the host system 510 of FIG. 5 mayhave attributes comparable to and may illustrate one possible embodimentof the host systems 110, 210, 310, and 410 shown in FIGS. 1-4,respectively. However, FIG. 5 describes an aspect of the host system510, focusing primarily on one particular implementation of IM hostcomplex 590.

The client system 505 includes a client device 520 and a clientcontroller 525. The client controller 525 is generally capable ofestablishing a connection to the host system 510, including the OSP hostcomplex 580, the IM host complex 590 and/or the Internet 565. In oneimplementation, the client controller 525 includes an IM application forcommunicating with servers in the IM host complex 590 utilizingexclusive IM protocols. The client controller 525 also may includeapplications, such as an OSP client application and/or an Internetbrowser application, for communicating with elements such as the OSPhost complex 580 and the Internet 565.

The host system 510 includes a host device 535 and a host controller540. The host controller 540 is generally capable of transmittinginstructions to any or all of the elements of the host device 535. Forexample, in one implementation, the host controller 540 includes one ormore software applications loaded on one or more elements of the hostdevice 535. However, in other implementations, as described above, thehost controller 540 may include any of several other programs, machines,and devices operating independently or collectively to control the hostdevice 535.

The host system 510 includes a login server 570 capable of enablingcommunications between client systems 505 and various elements of thehost system 5 10, including elements such as the OSP host complex 580and IM host complex 590; login server 570 is also capable of authorizingaccess by the client system 505 and those elements. The login server 570may implement one or more authorization procedures to enablesimultaneous access to one or more of the elements. The OSP host complex580 and the IM host complex 590 are connected through one or more hostcomplex gateways 585 and one or more IM host complex gateways 595. EachOSP host complex gateway 585 and IM host complex gateway 595 may performany protocol conversions necessary to enable communication between theOSP host complex 580, the IM host complex 590, and the Internet 565.

To access the IM host complex 590 to begin an instant messaging session,the client system 505 establishes a connection to the login server 570.The login server 570 typically determines whether the particularsubscriber is authorized to access the IM host complex 590 by verifyinga subscriber identification and password. If the subscriber isauthorized to access the IM host complex 590, the login server 570employs a hashing technique on the subscriber's screen name to identifya particular IM server 5902 for use during the subscriber's session. Thelogin server 570 provides the client system 505 with the IP address ofthe particular IM server 5902, gives the client system 505 an encryptedkey (i.e., a cookie), and breaks the connection. The client system 505then uses the IP address to establish a connection to the particular IMserver 5902 through the communications link 515, and obtains access tothat IM server 5902 using the encrypted key. Typically, the clientsystem 505 will be equipped with a winsock API (“Application ProgrammingInterface”) that enables the client system 505 to establish an open TCPconnection to the IM server 5902.

Once a connection to the IM server 5902 has been established, the clientsystem 505 may directly or indirectly transmit data to and accesscontent from the IM server 5902 and one or more associated domainservers 5904. The IM server 5902 supports the fundamental instantmessaging services and the domain servers 5904 may support associatedservices, such as, for example, administrative matters, directoryservices, chat and interest groups. The domain servers 5904 can be usedto lighten the load placed on the IM server 5902 by assumingresponsibility for some of the services within the IM host complex 590.By accessing the IM server 5902 and/or the domain server 5904, asubscriber can use the IM client application to view whether particularsubscribers (“buddies”) are online, exchange instant messages withparticular subscribers, participate in group chat rooms, trade filessuch as pictures, invitations or documents, find other subscribers withsimilar interests, get customized news and stock quotes, and search theWeb.

In the implementation of FIG. 5, IM server 5902 is directly orindirectly connected to a routing gateway 5906. The routing gateway 5906facilitates the connection between the IM server 5902 and one or morealert multiplexors 5908. For example, routing gateway 5906 may serve asa link minimization tool or hub to connect several IM servers 5902 toseveral alert multiplexors 5908. In general, an alert multiplexor 5908maintains a record of alerts and subscribers registered to receive thealerts.

Once the client system 505 is connected to the alert multiplexor 5908, asubscriber can register for and/or receive one or more types of alerts.The connection pathway between the client system 505 and the alertmultiplexor 5908 is determined by employing a hashing technique at theIM server 5902 to identify the particular alert multiplexor 5908 to beused for the subscriber's session. Once the particular multiplexor 5908has been identified, the IM server 5902 provides the client system 505with the IP address of the particular alert multiplexor 5908 and givesthe client system 505 an encrypted key (i.e., a cookie) used to gainaccess to the identified multiplexor 5908. The client system 505 thenuses the IP address to connect to the particular alert multiplexor 5908through the communication link 515 and obtains access to the alertmultiplexor 5908 using the encrypted key.

The alert multiplexor 5908 is connected to an alert gate 5910 that, likethe IM host complex gateway 595, is capable of performing the necessaryprotocol conversions to enable communication with the OSP host complex580. The alert gate 5910 is the interface between the IM host complex590 and the physical servers, such as servers in the OSP host complex580, where state changes are occurring. In general, the informationregarding state changes will be gathered and used by the IM host complex590. However, the alert multiplexor 5908 also may communicate with theOSP host complex 580 through the IM gateway 595, for example, to providethe servers and subscribers of the OSP host complex 580 with certaininformation gathered from the alert gate 5910.

The alert gate 5910 can detect an alert feed corresponding to aparticular type of alert.

The alert gate 5910 may include a piece of code (alert receive code)capable of interacting with another piece of code (alert broadcast code)on the physical server where a state change occurs. In general, thealert receive code installed on the alert gate 5910 instructs the alertbroadcast code installed on the physical server to send an alert feed tothe alert gate 5910 upon the occurrence of a particular state change.Thereafter, upon detecting an alert feed, the alert gate 5910 contactsthe alert multiplexor 5908, which in turn, informs the appropriateclient system 505 of the detected alert feed.

In the implementation of FIG. 5, the IM host complex 590 also includes asubscriber profile server 5912 connected to a database 5914 for storinglarge amounts of subscriber profile data. The subscriber profile server5912 may be used to enter, retrieve, edit, manipulate, or otherwiseprocess subscriber profile data. In one implementation, a subscriber'sprofile data includes, for example, the subscriber's buddy list, alertpreferences, designated stocks, identified interests, geographiclocation and other demographic data. The subscriber may enter, editand/or delete profile data using an installed IM client application onthe client system 505 to interact with the subscriber profile server5912.

Because the subscriber's data is stored in the IM host complex 590, thesubscriber does not have to reenter or update such information in theevent that the subscriber accesses the IM host complex 590 using a newor different client system 505. Accordingly, when a subscriber accessesthe IM host complex 590, the IM server 5902 can instruct the subscriberprofile server 5912 to retrieve the subscriber's profile data from thedatabase 5914 and to provide, for example, the subscriber's buddy listto the IM server 5902 and the subscriber's alert preferences to thealert multiplexor 5908. The subscriber profile server 5912 also maycommunicate with other servers in the OSP host complex 590 to sharesubscriber profile data with other services. Alternatively, user profiledata may be saved locally on the client device 505.

Referring to FIG. 6, a communications system 600 is capable ofdelivering and exchanging information between a client system 605 and ahost system 610 through a communication link 615. Client system 605typically includes one or more client devices 620 and one or more clientcontrollers 625 for controlling the client devices 620. Host system 610typically includes one or more host devices 635 and one or more hostcontrollers 640 for controlling the host devices 635. The communicationslink 615 may include communication pathways 650, 655 enablingcommunications through the one or more delivery networks 660.

Examples of each element within the communication system of FIG. 6 arebroadly described above with respect to FIGS. 1-5. In particular, theclient system 605 and the communications link 615 typically haveattributes comparable to those described with respect to client systems105, 205, 305, 405 and 505 and communications links 115, 215, 315, 415and 515 of FIGS. 1-5, respectively. Likewise, the host system 610 ofFIG. 6 may have attributes comparable to and may illustrate one possibleembodiment of the host systems 110, 210, 310, 410 and 510 shown in FIGS.1-5, respectively. However, FIG. 6 describes several aspects of oneimplementation of the host system 610 in greater detail, focusingprimarily on one particular implementation of the login server 670 andIM host complex 690.

The client system 605 includes a client device 620 and a clientcontroller 625. The client controller 625 is generally capable ofestablishing a connection to the host system 610, including the IM hostcomplex 690. In one implementation, the client controller 625 includesan IM application for communicating with servers in the IM host complex690 utilizing exclusive IM protocols.

The host system 610 includes a host device 635 and a host controller640. The host controller 640 is generally capable of transmittinginstructions to any or all of the elements of the host device 635. Forexample, in one implementation, the host controller 640 includes one ormore software applications loaded on one or more elements of the hostdevice 635. However, in other implementations, as described above, thehost controller 640 may include any of several other programs, machines,and devices operating independently or collectively to control the hostdevice 635.

The host system 610 includes a login server 670 capable of enablingcommunications between client systems 605 and various elements of thehost system 610, including elements such as the IM host complex 690 andthe OSP host complex 680; login server 670 is also capable ofauthorizing access by the client system 605 and those elements. The IMhost complex 690 includes an IM server network 6902, a routing gateway6906, an alert multiplexor network 6908, and one or more alert gates6910. The IM server network 6902 may include an interconnected networkof IM servers and the alert multiplexor network 6908 may include aninterconnected network of alert multiplexors. In the implementation ofFIG. 6, the IM server network 6902 and the alert multiplexor network6908 are interconnected by a routing gateway 6906 that serves as acommon hub to reduce the number of connections. Each IM server within IMserver network 6902 can directly or indirectly communicate and exchangeinformation with one or more of the alert multiplexors in the alertmultiplexor network 6908. Each of the alert multiplexors in the alertmultiplexor network 6908 may be connected to several alert gates 6910that receive different types of alerts.

During a session, a subscriber typically will be assigned to one IMserver in the IM server network 6902 and to one alert multiplexor in thealert multiplexor network 6908 based on one or more hashing techniques.In one implementation, for example, each IM server in the IM servernetwork 6902 may be dedicated to serving a particular set of registeredsubscribers. Because all of the IM servers can communicate with eachother, all subscribers can communicate with each other through instantmessaging. However, the IM servers and the alert multiplexors arecapable of storing subscriber information and other electronic contentthat may be accessed by the other IM servers and alert multiplexors.Thus, in another implementation, each alert multiplexor in the alertmultiplexor network 6908 may be dedicated to storing information about aparticular set or subset of alerts. Because all of the alertmultiplexors can communicate with each other, all registered subscriberscan receive all types of alerts. This networking arrangement enables theload to be distributed among the various servers in the IM host complex690 while still enabling a subscriber to communicate, share information,or otherwise interact with other subscribers and servers in the IM hostcomplex 690.

FIG. 7 is a block diagram illustrating the contents 700 of memory withina client communication system that is configured to communicate with ahost communication system. The client communication system is generallyillustrated by items 105, 205, 305, 405, 505, and 605 of FIGS. 1-6. Thehost communication system with which the client communication systemcommunicates is generally illustrated by items 110, 210, 310, 410, 510,and 610 of FIGS. 1-6. However, either may be incorporated into othertypes of communication systems.

As shown, the memory contents 700 of the client communication systeminclude system software 710, client software 720, and other software730. The system software 710 generally includes programs and dataenabling operation of the client communication system, and the othersoftware 730 generally includes other programs and data enabling theperformance of applications and storage and retrieval of data using theclient communication system. The system software 710 and other software730 are generally stored in the memory of a client device such as thatshown and described with respect to items 120, 220, 320, 420, 520, and620 of FIGS. 1-6.

The client software 720 generally includes programs and data filescapable of enabling communication between the client communicationsystem and the host communication system. The client software 720 isgenerally stored on the client communication system and loaded into thememory of a client controller, such as that shown and described withrespect to items 125, 225, 325, 425, 525, and 625 of FIGS. 1-6, whencommunications are to be initiated with a host communication system.

The client software 720 generally includes configuration data for acommunication device (e.g., modem) resident on the client communicationsystem, and information for contacting the host communication system.The client software 720 also generally includes information (e.g., loginand password information) for performing handshaking with the hostcommunication system, and may include other information such as userpreference information.

The client software 720 generally includes several modules (not shown)for performing various functions. Modules of the client software 720 mayinclude user-dependent software 722, user-independent software 724, or acombination of the two. User-dependent software 722 includes datarelated to particular users, such as demographic data, personalizableconfiguration data, and user-specific login data. The software 722 alsomay include data reflecting user system attributes, such as modem typeand speed, and processor characteristics. By contrast, user-independentsoftware 724 generally includes static information within the clientsoftware, such as fixed instructions and read only modules.

As will be described, identification of unauthorized clientcommunication systems will generally be performed based on an inspectionof user-independent software 724 since the contents of theuser-independent software 724 can be predicted for the machines ofdifferent users. However, it may be possible to otherwise classify theclient software to enable identification based on different criteria.

In general, the client software 720 is loaded at a predesignatedlocation within the memory of the client communication system. However,because that memory may include other software loaded at thepredesignated location, at least a portion of the client software 720may be configured to load into an alternative location within the clientcommunication system memory. This alternative location may bepredesignated in the client software 720 or may be selectable by theclient communication system. One implementation uses this distinction toclassify the client software 720 based on the potential for volatilityof the software's location within the memory of the client communicationsystem. Specifically, portions of the client software 720 may bedistinguished based on whether their contents are permitted to be loadedat locations that differ from predesignated memory locations. Similarly,portions of the client software may be distinguished based on whethertheir contents may be changed by their relocation or the relocation ofother portions of the client software, e.g., due to an addressing schemeinterrelating the portions of the client software 720.

Based on criteria of this type, the client software 720 may be parsedinto virtual segments that remain static and virtual segments that maybe dynamic. By combining this classification with the classificationamong user-dependant and user-independent segments discussed above withrespect to FIG. 7, it is possible to identify the specific portions ofthe client software 720 that remain unchanged, notwithstandingvariations in the user or memory location. Specific portions of clientsoftware 720 may be deemed unchanged for purposes of identificationwhen, for instance, they are stored without interruption in the memoryof a client communication system (i.e., no pointers to relocated code),or when they are simply unchanged with respect to the user or user'ssystem (i.e., unmodified content). Specific portions of the clientsoftware 720 that are known to remain unchanged may be located on theclient communication system and used for authentication as describedbelow.

Although the software 710-730 shown by FIG. 7 appears to have asequential orientation left-to-right, the relative orientation of thesememory contents 700 may be arranged in any manner designated by theclient communication system. Furthermore, although shown as beingpositioned at a single portion of the memory, at least the clientsoftware 720 may be disbursed among several portions of the memory.

FIG. 8 is a block diagram illustrating an exemplary method 800 performedto identify an unauthorized client communication system seeking accessto a host communication system. The processes described with respect toFIG. 8 are generally performed by a software module on the hostcommunication system described above with respect to items 110, 210,310, 410, 510, and 610 of FIGS. 1-6.

The method 800 includes locating a memory segment of a clientcommunication system that stores client software (step 801), determiningwhether the client software stored in the memory segment of a clientcommunication system seeking access is official client software (step802), and sending a message to the client communication system andsuspending or terminating communication with the client communicationsystem when the client software is not official client software (step803).

Locating a memory segment may include identifying a type or version ofthe client software, in which the memory segment storing client softwareis known. Locating the memory segment also may include receivinginformation from the client communication system during or after aninitiation of communications, and determining the type or version of theclient software being used by the client communication system to enablecommunications with a host communication system. For example, during orafter an initiation of communications, performing a diagnosis on theclient communication system may be performed to automatically determinethe type or version of the client software.

Using the identified client type and/or version, it may be possible tolocate a memory segment of the client communication system that storesclient software by locating a memory segment that includes static clientsoftware that remains unchanged in memory segments of the officialclient communication systems, regardless of the client communicationsystem upon which it is stored. For instance, one or more memorysegments may be identified as including static client software thatremains unchanged based on the particular type of client communicationsystem upon which it is stored. The memory segment may also be locatedbased on a random selection among several memory segments that includethe client software, or based on a random selection among only theseveral memory segments that include client software that remainsunchanged as described above.

To determine whether the software stored in the memory segment includesofficial software (step 802), the client software stored in the memorysegment of the client communication system seeking access may becompared against corresponding client software within an official clientcommunication system. This comparison may involve a comparison of theactual software stored on the memory segment with official clientsoftware from an official client communication system, or it may insteadinvolve a comparison of the results of mathematical computationsperformed on each. For instance, the comparing may include performing amathematical computation on the contents of the identified memorysegment, performing the same computation on the corresponding segment ofthe official system, and comparing the results from the mathematicalcomputations. The mathematical computations may include a hashingalgorithm, such as a message digest algorithm (e.g., MD3, MD5) or asecured hash algorithm (e.g., SHA1), or other algorithms.

As illustrated in FIG. 8, several actions may be taken in response to afailure to authenticate, including one or more of terminating thecommunication session immediately or after a delay, requestingadditional authenticating information, displaying an error message, andblocking further communication from the Internet protocol (IP) addressof the accessing system. Other responses also may be appropriate.

FIG. 9 provides an exemplary view of the logical configuration 910 ofsoftware and hardware elements within the communication system and anexemplary process 920 performed by those logical elements. FIGS. 10A,10B, and 10C show aspects 100A, 100B, and 100C, respectively, of theprocess used to identify unauthorized communication systems. In FIGS.10A-10C, each of the illustrated system components is represented by avertical line consisting of solid and broken line segments. The verticaldimension of each figure represents time (e.g., points lower in thefigure represent later times than points higher in the figure), althoughnot necessarily to scale. The solid segments of each component linedenote periods of time during which a particular component is active,each being labeled with a brief description of the activity that thecomponent is then performing. The broken line segments denote periods oftime when the component is inactive, with respect to this process. Thehorizontal arrows denote interactions between two components, the arrowspointing from the originating component to the receiving component. Thearrow labels describe the data being transferred between the components.

More specifically, FIG. 9 shows an example of logical interconnections910 among several software and hardware elements. In the implementationshown by FIG. 9 and referenced by FIGS. 10A-10C, four (4) elements arespecifically called out—client 91, host 92, timer 93, and archive 94.

Client 91 represents software loaded in the memory of a clientcommunication system, such as that shown and described above withreference to FIGS. 1-7.

Host 92 represents software loaded in the memory of a host communicationsystem, such as that shown and described above with reference to FIGS.1-6. As described previously with respect to FIGS. 1-7, the client 91and host 92 may communicate using the Internet or some othercommunication medium.

Timer 93 represents a timing mechanism that may be implemented usinghardware and/or software, e.g., a hardware device together withcontrolling software. Timer 93 is typically integrated into theoperating system of the host communication system. As such, host 92 mayprogram timer 93 to provide an alert after a specified interval haselapsed.

Archive 94 represents a storage medium (e.g., a disk) storing one ormore versions (e.g., database) of officially sanctioned client softwarecurrently available to access the host communication system. The archivemay reside in storage on the host communication system, or in storage onanother computer or communication system that is accessible to the hostcommunication system. The archive may be indexed using client platform(e.g. Windows, Macintosh) and version number, or otherwise asappropriate.

Process 100A of FIG. 10A illustrates an example of an initial exchangebetween the client 91 and host 92. Specifically, during the sign-onstage, the client 91 sends a message (step 101) identifying its platform(i.e. hardware and operating system) and implementation version to host92. Based on this information, host 92 requests a memory map of client91 from archive 94 (steps 102, 103, 104). The requested memory mapdistinguishes locations in the memory of client 91 that remainunchanged, and hence remain predictable, from locations within theclient memory that remain subject to change. The unchanged portions ofmemory tend to maintain identical contents both in client 91 and inarchive 94. Therefore, using the memory map, host 92 randomly selects(step 105) one or more contiguous segments from the unchanged locations.For each selected segments, the host 92 then transmits a descriptor(step 106) identifying the segment location to client 91. The descriptortypically includes the location of the segment module, its offset withinthat module, and its length. Concurrently, the host 92 starts (107) thetimer 93.

Thereafter, a first scenario, depicted in FIG. 10B, maybe experienced byofficial and unofficial clients. Under this scenario, upon receiving thesegment descriptors, the client computes a message digest of therequested segments (steps 108 and 109). In one implementation, twodigest algorithms are used: the “null” algorithm, which simply returns aconcatenation of the bytes in the segments, and the message-digestalgorithm (e.g., MD5 developed by RSA Data Security, Inc). Variousdigest algorithms may be substituted for the message-digest algorithm,but message digests in which it is computationally infeasible to producetwo different messages with the same digest are preferred. Both the nullalgorithm and MD5 have this property.

Upon receiving the digest, the host 92 stops the timer 93 (step 110),and retrieves its own copy of the selected segments from the archive 94(steps 111, 112 and 113). It then independently computes the digest(step 114) and compares its result with the digest obtained from theclient 91 (step 115). If the digests match, the client 91 is permittedto stay online. If the digests do not match, the client 91 is presumedan unauthorized communication system that is therefore disconnected(step 116).

Conversely, a second scenario, depicted in FIG. 10B, may arise whenclients 91 do not respond with a digest. If the host 92 does not receivea digest from the client 91, it will not stop the timer 93 (step 110).The timer 93 will expire approximately 30 seconds from the time it wasstarted and will notify the server 91 (step 117). At this point, thehost 92 will disconnect the client 91 (step 118).

Any or all of the processes described above may be implemented during aninitiation of communications between the client communication system andthe host communication system, or at any time thereafter. For instance,the above process may be implemented after communications have beenongoing for a fixed or random period of time.

A number of implementations have been described above. Nevertheless, itwill be understood that various modifications may be made withoutdeparting from the spirit and scope of the invention.

For instance, the above features may be applied to any system involvingcommunication between two or more computer systems where it is necessaryfor one or more of the computer systems to authenticate another of thecomputer systems. Particular utility exists for application serviceproviders (e.g., instant messaging application providers) and e-commercedriven systems seeking to authenticate computer systems seeking orreceiving access thereto. When used in this manner, this process andsystem may prevent access to host communication systems by unauthorizedcomputer systems, thereby preventing harms such as loss of advertisingrevenue, loss of revenue otherwise generated through the controlledredirection of those users, and loss of service contract revenuesresulting from defection of clients otherwise chasing service contractsunder the host communication systems.

The above system and process may also be used to verify that other typesof specified software applications are loaded and operating on anymachine being checked, and the like.

As described, one aspect of the above implementations authenticates aclient communication system by focusing on properties of an officialclient communication system rather than on the peculiarities in thebehavior of impostor clients.

Another aspect of the above implementations involves the random use ofvarious memory contents for authentication, thus requiring an impostorclient to duplicate virtually every aspect of the official clientsoftware object code in order to consistently authenticate. Suchduplication may increase the size of the imposter client systemsoftware, requiring increased the download time and footprint sizetherefor.

Still other aspects of the above implementations involve varying thetiming of the authentication, and varying the response to unauthorizedclient communication systems. Taken independently or in combination withvariations in the memory location being used for authentication, theseaspects make it difficult for third parties to determine how thisauthentication is performed, and thus difficult to defeat.

Yet another aspect of the overall implementation involves the transferand comparison of results from mathematical computations performed onmemory segments, rather than transferring and comparing the contents ofthe memory segments themselves. Using this manner, bandwidthrequirements and download time are reduced.

1. A method for identifying unauthorized client software seeking tocommunicate with a host communication system, comprising: locating amemory segment within a client communication system that stores clientsoftware used to communicate with a host communication system;determining whether the client software stored in the memory segmentlocated corresponds to client software for an official clientcommunication system; and identifying the client communication system asan unauthorized client communication system when the client softwarestored in the memory segment located does not correspond to the clientsoftware for an official client communication system.
 2. The method ofclaim 1, wherein locating the memory segment comprises: identifying atype or version of client software being used by the clientcommunication system to enable communication, and locating the memorysegment of the client communication system based on the identified typeor version.
 3. The method of claim 2, wherein identifying the type orversion comprises receiving information indicating the type or versionof the client software from the client communication system when acommunication session is initiated.
 4. The method of claim 2, whereinidentifying the type or version comprises performing a diagnostic on theclient communication system to automatically determine the type orversion of the client software.
 5. The method of claim 1, whereinlocating the memory segment comprises locating a memory segment of theclient communication system that includes client software that remainsunchanged in memory segments of official client communication systems.6. The method of claim 1, wherein locating the memory segment compriseslocating a memory segment of the client communication system thatincludes client software that is user independent in memory segments ofofficial client communication systems.
 7. The method of claim 1, whereinlocating the memory segment comprises identifying the memory segmentbased on a random selection among several memory segments that store theclient software.
 8. The method of claim 7, wherein identifying thememory segment comprises identifying the memory segment based on arandom selection among several memory segments including client softwarethat remains unchanged with respect to each particular client.
 9. Themethod of claim 8, wherein identifying the memory segment comprisesidentifying the memory segment based on a random selection among severalmemory segments including a continuous piece of client software on thememory segment that is stored without relocation of any intermediateclient software.
 10. The method of claim 1, wherein determining whetherthe client software corresponds to official software comprises comparingthe client software stored in the identified memory segment with thecorresponding client software of the official client communicationsystem.
 11. The method of claim 10, wherein comparing the clientsoftware comprises: performing a mathematical computation on thecontents of the identified memory segment; and comparing results fromthe mathematical computation performed on the contents of the identifiedmemory segment against a mathematical representation for thecorresponding client software of the official communication system. 12.The method of claim 11, wherein the mathematical computation comprises achecksum.
 13. The method of claim 11, wherein the mathematicalcomputation comprises a hashing algorithm.
 14. The method of claim 13,wherein terminating communications is performed after a predeterminedand intentional delay once the client communication system is identifiedas an unauthorized client communication system.
 15. The method of claim1, further comprising terminating communications from the clientcommunication system when the client software stored in the memorysegment is determined to diverge from predictable client software for anofficial client communication system.
 16. The method of claim 1, furthercomprising sending a notification to the user of the clientcommunication system indicating identification of an unauthorized clientwhen the client software stored in the memory segment is determined todiverge from predictable client software for an official clientcommunication system.
 17. The method of claim 1 wherein the clientsoftware used for communicating includes software configured to performprocessing independent of authentication.
 18. The method of claim 17wherein the client software used for communicating includes softwareconfigured to perform processing independent of authentication of theclient communication system.
 19. The method of claim 17 wherein theclient software used for communicating includes software configured toperform processing independent of authentication of a user of the clientcommunication system.
 20. The method of claim 1 wherein the clientsoftware used for communicating includes software for identifyingunauthorized client software.
 21. The method of claim 1 wherein locatinga memory segment, determining whether the client software corresponds toclient software for an official client communication system, andidentifying the client communication system as an unauthorized clientcommunication system are performed for the purpose of identifyingunauthorized client software.
 22. The method of claim 1 wherein theclient software used for communicating includes executable software. 23.The method of claim 1 wherein the client software used for communicatingincludes a client application.
 24. The method of claim 1 wherein theclient software used for communicating includes a browser application.25. The method of claim 1 further comprising, in addition to determiningwhether the client software corresponds to client software for anofficial client communication system, determining whether a user of theclient software is an authorized user.
 26. The method of claim 1 whereinlocating a memory segment within a client communication system,determining whether the client software stored in the memory segmentlocated corresponds to client software for an official clientcommunication system, and identifying the client communication system asan unauthorized client communication system occur after initiation of acommunication session between the client communication system and thehost system.
 27. The method of claim 26 wherein locating a memorysegment within a client communication system, determining whether theclient software stored in the memory segment located corresponds toclient software for an official client communication system, andidentifying the client communication system as an unauthorized clientcommunication system occur before the communication session between theclient communication system and the host system ends.
 28. A computerreadable medium or propagated signal having embodied thereon a computerprogram, that when executed by a processor, identifies unauthorizedclient software seeking to communicate with a host communication system,the computer program comprising: a locating code segment for locating amemory segment within a client communication system that stores clientsoftware used to communicate with a host communication system; adetermining code segment for determining whether the client softwarestored in the memory segment located corresponds to client software foran official client communication system; and an identifying code segmentfor identifying the client communication system as an unauthorizedclient communication system when the client software stored in thememory segment located does not correspond to the client software for anofficial client communication system.
 29. The medium of claim 28,wherein the locating code segment comprises: an identifying code segmentfor identifying a type or version of client software being used by theclient communication system to enable communication, and a locating codesegment for locating the memory segment of the client communicationsystem based on the identified type or version.
 30. The medium of claim29, wherein the identifying code segment comprises a receiving codesegment for receiving information indicating the type or version of theclient software from the client communication system when acommunication session is initiated.
 31. The medium of claim 29, whereinthe identifying code segment comprises a performing code segment forperforming a diagnostic on the client communication system toautomatically determine the type or version of the client software beingused by the client communication system to enable communication.
 32. Themedium of claim 28, wherein the locating code segment comprises a codesegment for locating a memory segment of the client communication systemthat includes client software that remains unchanged in memory segmentsof official client communication systems.
 33. The medium of claim 28,wherein the locating code segment comprises a code segment for locatinga memory segment of the client communication system that includes clientsoftware that is user independent in memory segments of official clientcommunication systems.
 34. The medium of claim 28, wherein the locatingcode segment comprises an identifying code segment for identifying thememory segment based on a random selection among several memory segmentsthat include the client software.
 35. The medium of claim 34, whereinthe identifying code segment comprises a code segment for identifyingthe memory segment based on a random selection among several memorysegments including client software that remains unchanged.
 36. Themedium of claim 28, wherein the determining code segment comprises acomparing code segment for comparing the client software stored in theidentified memory segment with the corresponding client software of theofficial client communication system.
 37. The medium of claim 36,wherein the comparing code segment comprises: a performing code segmentfor performing a mathematical computation on the contents of theidentified memory segment; and a comparing code segment for comparingresults from the mathematical computation performed on the contents ofthe identified memory segment against a mathematical representation forthe corresponding client software of the official communication system.38. The medium of claim 37, wherein the mathematical computationcomprises a checksum.
 39. The medium of claim 37, wherein themathematical computation comprises a hashing algorithm.
 40. The mediumof claim 28, further comprising a terminating code segment forterminating communications from the client communication system when theclient software stored in the memory segment is determined to divergefrom predictable client software for an official client communicationsystem.
 41. The medium of claim 28 wherein the client software used forcommunicating includes software configured to perform processingindependent of authentication.
 42. The medium of claim 41 wherein theclient software used for communicating includes software configured toperform processing independent of authentication of the clientcommunication system.
 43. The medium of claim 41 wherein the clientsoftware used for communicating includes software configured to performprocessing independent of authentication of a user of the clientcommunication system.
 44. The medium of claim 28 wherein the clientsoftware used for communicating includes software for identifyingunauthorized client software.
 45. The medium of claim 28 whereinlocating a memory segment, determining whether the client softwarecorresponds to client software for an official client communicationsystem, and identifying the client communication system as anunauthorized client communication system are performed for the purposeof identifying unauthorized client software.
 46. The medium of claim 28wherein the client software used for communicating includes executablesoftware.
 47. The medium of claim 28 wherein the client software usedfor communicating includes a client application.
 48. The medium of claim28 wherein the client software used for communicating includes a browserapplication.
 49. The medium of claim 28 further comprising one or morecode segments configured to determine whether a user of the clientsoftware is an authorized user, wherein the determination of whether auser is an authorized user is made in addition to determining whetherthe client software corresponds to client software for an officialclient communication system.
 50. The medium of claim 28 wherein thelocating code segment, the determining code segment, and the identifyingcode segment are executed after initiation of a communication sessionbetween the client communication system and the host system.
 51. Themedium of claim 50 wherein the locating code segment, the determiningcode segment, and the identifying code segment are executed before thecommunication session between the client communication system and thehost system ends.
 52. A communication system for identifyingunauthorized client software seeking to communicate with thecommunication system, the communication system comprising: a locatorstructured and arranged to locate a memory segment within a clientcommunication system that stores client software used to communicatewith the communication system; a comparing device structured andarranged to determine whether the client software stored in the memorysegment located corresponds to client software for an official clientcommunication system; and an identifier structured and arranged toidentify the client communication system as an unauthorized clientcommunication system when the client software stored in the memorysegment located does not correspond to the client software for anofficial client communication system.
 53. The communication system ofclaim 52, wherein the locator comprises: an identifier structured andarranged to identify a type or version of client software being used bythe client communication system to enable communication, and a locatorstructured and arranged to locate the memory segment of the clientcommunication system based on the identified type or version.
 54. Thecommunication system of claim 53, wherein the identifier comprises areceiver structured and arranged to receive information from the clientcommunication system when the communication session is initiatedindicating the type or version of client software.
 55. The communicationsystem of claim 53, wherein the identifier comprises a testing devicestructured and arranged to perform a diagnostic on the clientcommunication system to automatically determine the type or version ofthe client software being used by the client communication system toenable communication.
 56. The communication system of claim 52, whereinthe locator comprises a memory segment locator structured and arrangedto locate a memory segment of the client communication system thatincludes client software that remains unchanged in memory segments ofofficial client communication systems.
 57. The communication system ofclaim 52, wherein the locator comprises a memory segment locatorstructured and arranged to locate a memory segment of the clientcommunication system that includes client software that is userindependent in memory segments of official client communication systems.58. The communication system of claim 52, wherein the locator comprisesan identifier structured and arranged to identify the memory segmentbased on a random selection among several memory segments that includethe client software.
 59. The apparatus of claim 58, wherein theidentifier comprises a memory segment identifier structured and arrangedto identify the memory segment based on a random selection among severalmemory segments including client software that remains unchanged. 60.The communication system of claim 52, wherein the comparing devicecomprises a comparing device structured and arranged to compare theclient software stored in the identified memory segment with thecorresponding client software of the official client communicationsystem.
 61. The communication system of claim 60, wherein the comparingdevice comprises: a testing device structured and arranged to test amathematical computation on the contents of the identified memorysegment; and a comparing device structured and arranged to compareresults from the mathematical computation performed on the contents ofthe identified memory segment against a mathematical representation forthe corresponding client software of the official communication system.62. The communication system of claim 61, wherein the mathematicalcomputation comprises a checksum.
 63. The communication system of claim61, wherein the mathematical computation comprises a hashing algorithm.64. The communication system of claim 52, further comprising a devicestructured and arranged to terminate communications from the clientcommunication system when the client software stored in the memorysegment is determined to diverge from predictable client software for anofficial client communication system.
 65. The apparatus of claim 52wherein the client software used for communicating includes softwareconfigured to perform processing independent of authentication.
 66. Theapparatus of claim 65 wherein the client software used for communicatingincludes software configured to perform processing independent ofauthentication of the client communication system.
 67. The apparatus ofclaim 65 wherein the client software used for communicating includessoftware configured to perform processing independent of authenticationof a user of the client communication system.
 68. The communicationsystem of claim 52 wherein the client software used for communicatingincludes software for identifying unauthorized client software.
 69. Thecommunication system of claim 52 wherein locating a memory segment,determining whether the client software corresponds to client softwarefor an official client communication system, and identifying the clientcommunication system as an unauthorized client communication system areperformed for the purpose of identifying unauthorized client software.70. The communication system of claim 52 wherein the client softwareused for communicating includes executable software.
 71. Thecommunication system of claim 52 wherein the client software used forcommunicating includes a client application.
 72. The communicationsystem of claim 52 wherein the client software used for communicatingincludes a browser application.
 73. The communication system of claim 52further comprising a determining device structured and arranged todetermine whether a user of the client software is an authorized user,wherein the determination of whether a user is an authorized user ismade in addition to determining whether the client software correspondsto client software for an official client communication system.
 74. Thecommunication system of claim 52 wherein locating a memory segmentwithin a client communication system, determining whether the clientsoftware stored in the memory segment located corresponds to clientsoftware for an official client communication system, and identifyingthe client communication system as an unauthorized client communicationsystem occur after initiation of a communication session between theclient communication system and the host system.
 75. The communicationsystem of claim 74 wherein locating a memory segment within a clientcommunication system, determining whether the client software stored inthe memory segment located corresponds to client software for anofficial client communication system, and identifying the clientcommunication system as an unauthorized client communication systemoccur before the communication session between the client communicationsystem and the host system ends.
 76. A method for identifying anunauthorized client communication system seeking access to a hostcommunication system, comprising: locating a memory segment within aclient communication system that stores client software used tocommunicate with a host communication system; determining whether theclient software stored in the memory segment located corresponds toclient software for an official client communication system; andidentifying the client communication system as an unauthorized clientcommunication system when the client software stored in the memorysegment located does not correspond to the client software for anofficial client communication system, wherein locating the memorysegment comprises locating a memory segment of the client communicationsystem that includes client software that is user independent in memorysegments of official client communication systems.
 77. A method foridentifying an unauthorized client communication system seeking accessto a host communication system, comprising: locating a memory segmentwithin a client communication system that stores client software used tocommunicate with a host communication system; determining whether theclient software stored in the memory segment located corresponds toclient software for an official client communication system; andidentifying the client communication system as an unauthorized clientcommunication system when the client software stored in the memorysegment located does not correspond to the client software for anofficial client communication system, wherein locating the memorysegment comprises identifying the memory segment based on a randomselection among several memory segments that store the client software.78. The method of claim 77, wherein identifying the memory segmentcomprises identifying the memory segment based on a random selectionamong several memory segments including client software that remainsunchanged with respect to each particular client.
 79. The method ofclaim 77, wherein identifying the memory segment comprises identifyingthe memory segment based on a random selection among several memorysegments including a continuous piece of client software on the memorysegment that is stored without relocation of any intermediate clientsoftware.
 80. A communication system for identifying an unauthorizedclient communication system seeking access to a host communicationsystem, the communication system comprising: a locator structured andarranged to locate a memory segment within a client communication systemthat stores client software used to communicate with the communicationsystem; a comparing device structured and arranged to determine whetherthe client software stored in the memory segment located corresponds toclient software for an official client communication system; and anidentifier structured and arranged to identify the client communicationsystem as an unauthorized client communication system when the clientsoftware stored in the memory segment located does not correspond to theclient software for an official client communication system, wherein thelocator comprises a memory segment locator structured and arranged tolocate a memory segment of the client communication system that includesclient software that is user independent in memory segments of officialclient communication systems.
 81. A communication system for identifyingan unauthorized client communication system seeking access to a hostcommunication system, the communication system comprising: a locatorstructured and arranged to locate a memory segment with a clientcommunication system that stores client software used to communicatewith the communication system; a comparing device structured andarranged to determine whether the client software stored in the memorysegment located corresponds to client software for an official clientcommunication system; and an identifier structured and arranged toidentify the client communication system as an unauthorized clientcommunication system when the client software stored in the memorysegment located does not correspond to the client software for anofficial client communication system, wherein the identifier comprises amemory segment identifier structured and arranged to identify the memorysegment based on a random selection among several memory segmentsincluding client software that remains unchanged.
 82. The communicationsystem of claim 81, wherein the identifier comprises a memory segmentidentifier structured and arranged to identify the memory segment basedon a random selection among several memory segments including clientsoftware that remains unchanged.
 83. The communicaton system of claim81, wherein the identifier comprises a memory segment identifierstructured and arranged to identify the memory segment based on a randomselection among several memory segments including a continuous piece ofclient software on the memory segment that is stored without relocationof any intermediate client software.